Are you running an INSERT, UPDATE, or DELETE command that is processing a large number of rows?
First check that the table is free of triggers. If the SQL is a DELETE, or you are updating a Primary or Unique key, make sure there are no referencing tables with Foreign Key clauses.
If these common problems don't apply, then you might be able to use one of these techniques to tune the DML.
Technique | Insert | Update | Delete |
---|---|---|---|
Direct Load Insert | Yes | No | No |
CREATE TABLE AS instead of INSERT on a partitioned table | Yes | No | No |
Updatable views | No | Yes | No |
Truncate and replace | No | Yes | Yes |
Drop and replace indexes | Yes | Yes | Yes |
Process by Rowid Range | Yes | Yes | Yes |